Payment Page (callback_form)

For each transaction, merchants are able to dynamically set the look and feel of the payment page, including the input boxes controlled by AltaPay, resulting in a seamless checkout flow all the way through to the payment.

Some alternative payment methods operate using a re-direct solution. In these instances, AltaPay takes care of all the mapping of the parameters the merchant already has integrated, reducing technical overhead.

Your customer accesses the payment page via our secure payment gateway. You design the page, and we retrieve it from your server in one of the following ways:

via the URL set in the config[callback_form] parameter in your call to the createPaymentRequest method, as described in Payment flow process (Merchant API). This is the recommended method.

For more information, see createPaymentRequest.

via the URL you set in the Callback url (form) field on the Terminal settings page found in the Home menu in the Merchant Information Interface. This method is not recommended.

To ensure that the page is secure, we deliver it using SSL from our gateway. All Javascript and other active content is stripped from its content. If the callback URL is non-secure (i.e. HTTP instead of HTTPS), all images, CSS, links, and forms are proxied by AltaPay.

You can clear the cache for all terminals under Home > Terminal in the Merchant Information Interface.

The payment page URL is retrieved via AltaPay's servers, and not directly by your customer, but cookies and UserAgent headers are relayed, and we will relay the UserAgent header if the client specifies this to us.

POST/GET parameters

The POST or GET request sent back to your payment page has the following parameters:

Parameter	Description	Type
shop_orderid	This is the internal ID of the order in your webshop. In most integrations, you can use the same order ID for up to four orders. For PayPal and MobilePay payments, you can only use it for a singe successful transaction. The shop_orderid value is posted back to you, so you know the order to which the payment refers.	[a-zA-Z0-9-]{1,100}
amount	This is the payment amount. If you are setting up a subscription, it is the default amount for each capture. You must use a dot as the decimal separator, and the amount can have maximum 2 decimals.	float
currency	This is the payment currency. It must be specified in an ISO-4217 format, either using the 3-digit numeric code, or the 3-letter character code. For more information about ISO-4217 currency codes, see https://en.wikipedia.org/wiki/ISO_4217.	[0-9]{3} or [A-Z]{3}
language	The language in which the payment form is displayed. For more information about supported language codes, see Supported languages. If the language parameter is not set, the language is derived from the browser's Accept-Language HTTP header field. If none of the browser languages are supported, the default is English, en. If the language you set is not supported, an error is returned.	[a-z]{2}
transaction_info	This is a one-dimensional associative array, where you can put any value that you would like to associate with the payment in the call to createPaymentRequest.	Array